Update Accessibility & Localization #199
Conversation
|
|
…umentation into pinkesh/accessibility-internationalisation
| - **Keyboard Navigation for Physical Impairments**: Users unable to use touchscreens can navigate the app effectively with keyboard controls. | ||
| - **Haptic Feedback**: Tactile responses help users with visual or motor impairments understand when interactions are successful. | ||
|
|
||
| ## Adding Accessibility |
There was a problem hiding this comment.
Is this heading necessary?
There was a problem hiding this comment.
I think we can go to the next paragraph right away as this section doesnt have much, only just creates the segue to the next section.
There was a problem hiding this comment.
Ya can do that!
|
|
||
| There are two ways you can manage the app text translation: | ||
|
|
||
| ### Inside Language Settings |
There was a problem hiding this comment.
This can be bullet points itself? Or just bold headings will work. No need for headers.
There was a problem hiding this comment.
ok, made it bold.
| In FlutterFlow, you can retrieve the following types of language-related data: | ||
|
|
||
| - **Current Language Code**: This provides the ISO language code for the current app language (e.g., en, de, fr). | ||
| - **Language-Dependent Text**: Allows you to specify different values for each language. For instance, you might want to display a country flag or name based on the current app language. |
There was a problem hiding this comment.
I havent used this much, so dont know much about this language dependent text. Who is specifying these values for each language? the user? From the image it seems to me that I can use this value on text properties but then I dont get "Allows you to specify different values for each language"
There was a problem hiding this comment.
Yes, it is set by the user. Think of it like conditional values based on language. It is helpful in cases where you don't want to show translated text instead, show something else like a flag or anything.
|
|
||
|  | ||
|
|
||
| ## Formatting Dates, Numbers, and Currency |
There was a problem hiding this comment.
| ## Formatting Dates, Numbers, and Currency | |
| ## Localizing Dates, Numbers, and Currency |
There was a problem hiding this comment.
Also as SEO & search point of view, I would rather not have this header and just have 3 main headers - Localizing Dates, Localizing Numbers etc because they are unrelated to each other right? So no point in keeping them under this header which anyway has no purpose as such other than just a single intro. So maybe we get rid of this header and promote the other headers?
There was a problem hiding this comment.
Good point! removed it.
| - **Change Device Locale**: Test your app by changing the device locale to verify translations and layout adjustments. | ||
| - **Use Emulators**: Use Android or iOS emulators to simulate different locales and ensure everything is displaying correctly. | ||
| - **Long Texts**: Verify that long translations do not overflow or cause UI issues. | ||
| - **Manual Testing**: Manually verify the accuracy of translations, date formats, number formats, etc. |
There was a problem hiding this comment.
I think somewhere in the doc (either here or as an example) we should mention about handling RTL languages
There was a problem hiding this comment.
I looked into it, but we don't support RTL languages natively in FF.
|
@PoojaB26 review comments are resolved. You can take a look again. |
Description
Update Accessibility & Localization
Linear ticket and magic word Fixes DEVR-376
Type of change